Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[skip changelog] Bump github.com/ProtonMail/go-crypto from 1.1.0-alpha.0 to 1.1.0-alpha.3-proton #2654

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 26, 2024

Bumps github.com/ProtonMail/go-crypto from 1.1.0-alpha.0 to 1.1.0-alpha.3-proton.

Release notes

Sourced from github.com/ProtonMail/go-crypto's releases.

v1.1.0-alpha.3-proton

This pre-release is v1.1.0-alpha.3 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-alpha.1-proton

This pre-release is v1.1.0-alpha.1 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-alpha.0-proton

This pre-release is v1.1.0-alpha.0 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-alpha.3

What's Changed

  • New functions to verify signature hash tags
  • Allow parsing certifications explicitly marked as exportable
  • Sorting signature sub-packets by their ID when serializing
  • Mark creation time, issuer key ID, and key flag signature sub-packets as critical
  • When AEAD is in use, the session key length is now determined by the cipher specified in the AEAD preference.

Full Changelog: v1.1.0-alpha.2...v1.1.0-alpha.3

v1.1.0-alpha.1

What's Changed

Removes the openpgp.VerifyDetachedSignatureAndSaltedHash function and the packet.SaltedHashSpecifier as they are no longer required. They were introduced for verifying the headers in cleartext messages. However, in the latest crypto-refresh specification, cleartext message headers were dropped.

Full Changelog: v1.1.0-alpha.0...v1.1.0-alpha.1

Commits
  • dfc5210 Fix HMAC generation (#204)
  • a0d3abb Replace ioutil.ReadAll with io.ReadAll
  • 12d80ee fix(v2): Adapt NewForwardingEntity to refactored NewEntity
  • 00db3be fix(v2): Do not allow encrpytion with a forwarding key
  • 49c1020 feat: Add symmetric keys to v2
  • bce9b31 fix: Address warnings
  • e202bef feat: Add forwarding to v2 api
  • 2a86d28 fix: Address rebase on version 2 issues
  • a425074 Use fingerprints instead of KeyIDs
  • b55bb97 Create a copy of the encrypted key when forwarding
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github.com/ProtonMail/go-crypto](https://github.com/ProtonMail/go-crypto) from 1.1.0-alpha.0 to 1.1.0-alpha.3-proton.
- [Release notes](https://github.com/ProtonMail/go-crypto/releases)
- [Commits](ProtonMail/go-crypto@v1.1.0-alpha.0...v1.1.0-alpha.3-proton)

---
updated-dependencies:
- dependency-name: github.com/ProtonMail/go-crypto
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Copy link

codecov bot commented Jun 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.23%. Comparing base (850f22a) to head (234aa4f).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2654   +/-   ##
=======================================
  Coverage   70.23%   70.23%           
=======================================
  Files         222      222           
  Lines       21347    21347           
=======================================
  Hits        14993    14993           
  Misses       5175     5175           
  Partials     1179     1179           
Flag Coverage Δ
unit 70.23% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 16, 2024

Superseded by #2666.

@dependabot dependabot bot closed this Jul 16, 2024
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/ProtonMail/go-crypto-1.1.0-alpha.3-proton branch July 16, 2024 12:56
@per1234 per1234 added the conclusion: duplicate Has already been submitted label Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conclusion: duplicate Has already been submitted topic: infrastructure Related to project infrastructure
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant